docs: add product/technical gap baseline - #41

sequenceDiagram
  participant Consumer
  participant SemanticUnitExactIndex
  participant RustCore
  participant PythonReport
  Consumer->>SemanticUnitExactIndex: provide snapshot and authorized identities
  SemanticUnitExactIndex->>RustCore: validate packed authorization and query batch
  RustCore->>RustCore: compute exact deterministic cosine scores
  RustCore-->>SemanticUnitExactIndex: return per-query reports and digests
  SemanticUnitExactIndex-->>PythonReport: convert native tuples to typed reports

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands.}

OpenCode Review Overview

• Head SHA: b7b63df3c09b68b627c8e17a060a55a5edc18351
• Workflow run: 32702757278
• Workflow attempt: 1
• Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head b7b63df3c09b68b627c8e17a060a55a5edc18351.

• Head SHA: b7b63df3c09b68b627c8e17a060a55a5edc18351

• Workflow run: 32702757278

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Docs: product-technical-gap-baseline.md"]
  S1 --> I1["operator or user guidance"]
  I1 --> R1["Review risk: Docs: product-technical-gap-baseline.md"]
  R1 --> V1["docs review"]

Exact-head product-contract update at 1becd61:

• added the standalone docs/product-requirements.md required before the Rust ownership implementation;
• corrected the stale LineageWeave boundary and removed an unsupported fixed consumer-weight claim from the gap baseline;
• added ADR 0006: one Rust core, Python adapter only, deterministic CPU parallelism across independent work, explicit optional GPU selection, and fail-closed bit-identical conformance instead of an arbitrary tolerance;
• added APA 7 references for IEEE 754-2019, CUDA 13.3 numerical guidance, PyO3 stable-ABI packaging, and Rayon reduction-order constraints.

Evidence: Ruff passed; 661 tests passed; statement and branch coverage are 100%; git diff --check passed. Hosted exact-head checks have restarted. No implementation or release claim is made by these documents.